Skip to content

Application password UX improvements#11079

Draft
johnbillion wants to merge 6 commits intoWordPress:trunkfrom
johnbillion:application-password-ux
Draft

Application password UX improvements#11079
johnbillion wants to merge 6 commits intoWordPress:trunkfrom
johnbillion:application-password-ux

Conversation

@johnbillion
Copy link
Member

Work in progress.

A collection of UX enhancements for the authorize-application.php screen, with a particular focus on hardening against phishing.

  • Greatly increase clarity about the target URL that will receive credentials if the request is approved
    • Shows the target host name front and centre without the rest of the URL
    • Gates approval behind a checkbox
  • Removes support for username:password@ credentials in URLs
    • These are almost exclusively used for phishing
    • Despite being deprecated in modern browsers for many years, they're still technically functional, but there is no need to support them
  • Removes support for reject URLs
    • If a user rejects approval, it is unexpected that they still get sent to the requesting site
    • This is an open redirect that can still result in phishing
    • Replaces the redirect with a message stating that the request was not approved
  • Adds a "Copy" button to the generated application password after approval
    • Matches the one used on the Application Passwords section of the user profile screen

Screenshots

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@domenico-ruggiano
Copy link

Great improvements here :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants